Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TTD Bid Adapter : revert integration type header due to CORS error #12800

Merged
merged 1 commit into from
Feb 24, 2025

Conversation

andre-gielow-ttd
Copy link
Contributor

@andre-gielow-ttd andre-gielow-ttd commented Feb 21, 2025

Type of change

  • Bugfix

  • Feature

  • New bidder adapter

  • Updated bidder adapter

  • Code style update (formatting, local variables)

  • Refactoring (no functional changes, no api changes)

  • Build related changes

  • CI related changes

  • Does this change affect user-facing APIs or examples documented on http://prebid.org?

  • Other

Description of change

Reverting these changes because of the following error:

Access to fetch at 'https://direct.adsrvr.org/bid/bidder/ezoic' from origin 'https://play2048.co' has been blocked by CORS policy: Request header field x-integration-type is not allowed by Access-Control-Allow-Headers in preflight response.

Prebid also gave a "Server call for ttd failed, continuing without bids" error, most likely due to the failed request.

I need to investigate why this is happening but to avoid other problems I'm reverting this for now while we check what is going on.

Other information

@ChrisHuie ChrisHuie changed the title Revert integration type header due to CORS error TTD Bid Adapter : revert integration type header due to CORS error Feb 24, 2025
@ChrisHuie ChrisHuie self-assigned this Feb 24, 2025
@andre-gielow-ttd
Copy link
Contributor Author

Will not merge this yet. Waiting for an internal change to kick in

@ChrisHuie ChrisHuie merged commit 86dccc4 into prebid:master Feb 24, 2025
6 checks passed
@andre-gielow-ttd
Copy link
Contributor Author

@ChrisHuie can un unmerge this? I'm waiting on an internal test to check if this will be actually required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants